Dynamic account selection

ABSTRACT

Embodiments automatically select one of the multiple pre-generated payment cards provisioned on a mobile device. The multiple pre-generated payment cards (real or virtual) may each have a different credit limit. The mobile device may automatically select one of the multiple payment cards based on a transaction value of a transaction that is being conducted. An available credit limit of the selected payment card may be equal to or slightly greater than the transaction value. In some embodiments, the available credit limit of the selected payment card may be closer to the transaction value than the available credit limits of the remaining payment cards. In some embodiments, the different payment cards may be provisioned in a chip-and-pin based smart credit card or mobile wallet.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application claims benefit under 35 USC § 119(e) to U.S.Provisional Patent Application No. 61/869,342 filed Aug. 23, 2013 andentitled “Dynamic Account Selection”, the disclosure of which isincorporated by reference herein in its entirety for all purposes.

BACKGROUND

There are a number of problems with conventional credit card usage.Conventional credit cards can be subjected to fraudulent transactions,and the risk of loss can be fairly significant. For example, if a creditcard with a very high credit limit is used to purchase a low value item,then the potential for loss can be fairly substantial. If, for example,a credit card with an available $10,000 credit limit is used to purchasea $2 sandwich at a restaurant. If an employee at the restaurant engagesin fraudulent behavior and wants to steal the credit card numberassociated with the credit card, then $9998 of available credit will beexposed to potential fraudulent use.

One solution to this problem is to allow a user to generate a temporarycard with a limited transaction value and/or expiration period. However,there are limitations to this mechanism. First, the user will need tomanually generate a new temporary card for each transaction. Second, theuser must always be connected to a remote host computer (thus needing anetwork connection and connection to the bank website/service) togenerate the temporary card number. Further, since the temporary card isnot a true credit card, it is limited in its use

Embodiments of the invention address these and other problems,individually and collectively.

BRIEF SUMMARY

Embodiments of the invention provide a way to provision a mobile devicewith multiple pre-generated payment cards (real or virtual) withdifferent credit limits. The mobile device may automatically select oneof the multiple payment cards based on a transaction value of atransaction that is being conducted. In some embodiments, the differentpayment cards may be provisioned in a chip-and-pin based smart creditcard or mobile wallet.

In embodiments of the invention, a request is made to a point of sale(POS) for a transaction value. Alternatively, the transaction value forthe transaction may be obtained otherwise. Based on the transactionvalue, the credit card with available credit limit close to thetransaction value is automatically selected by a processor, and isexposed for use in the transaction. In some embodiments, the credit cardmay be selected based on the transaction value being a pre-determinedpercentage of the available credit limit. Alternatively, the credit cardwith the closest limit (i.e. lowest allowable limit that would permit toconduct the transaction) may be automatically selected. The user mayalso store the credit card in a cloud wallet for online transactionswhere the credit card with lowest allowable limit may be used.

One embodiment of the invention is directed to a method includingreceiving, using a processor, information about a transaction, theinformation including a transaction value. The method may also includeautomatically selecting, using the processor, a payment account within aplurality of payment accounts associated with a plurality of limits. Theavailable credit limit associated with the selected payment account isclose to the transaction value. The method further includes providing,by the processor, payment account data associated with the selectedpayment account to an access device.

Another embodiment is directed to a mobile device comprising a processorand a computer readable medium coupled to the processor. The computerreadable medium comprises code that, when executed on the processor,causes the processor to receive information about a transaction, theinformation including a transaction value; automatically select apayment account within a plurality of payment accounts associated with aplurality of limits. The available credit limit associated with theselected payment account is close to the transaction value. The code,when executed on the processor, further causes the processor to providepayment account data associated with the selected payment account to anaccess device.

Yet another embodiment is directed to a method including receiving, atan access device, a request for a transaction value. The method alsoincludes sending, from the access device, a reply to the request, thereply including the transaction value. The method further includesreceiving, at the access device, payment account data to be used for thetransaction. An available credit limit associated with the paymentaccount is close to the transaction value, the limit being slightlygreater than or equal to the transaction value. The method also includesprocessing the transaction using the payment account data.

These and other embodiments of the invention are described in furtherdetail below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a flowchart illustrating methods according to embodimentsof the invention.

FIG. 2 shows a diagram of a payment card.

FIG. 3 shows a block diagram of a mobile device according an embodimentof the invention.

FIG. 4 shows a diagram illustrating different payment cards provided ona mobile device.

FIG. 5 shows a flowchart of a method for automatically selecting apayment card among a plurality of payment cards based on a transactionvalue.

FIG. 6 shows a flowchart of a method for receiving automaticallyselected payment card for a transaction in response to sending thetransaction value to a user device.

FIG. 7 shows a block diagram of an exemplary financial transactionsystem.

FIG. 8 shows a block diagram of some components of a computer apparatus.

DETAILED DESCRIPTION

Embodiments are directed at systems, methods, and devices forprovisioning a mobile device with pre-generated payment cards (real orvirtual) and/or payment account numbers with different credit limits.The different payment cards or account numbers can be used for differenttransactions with different transactional values. One of the paymentcards is automatically selected and used (i.e. exposed) based on thevalue of the transaction being conducted. In other embodiments, thedifferent payment cards or account numbers can be provisioned in achip-and-pin based smart credit card or mobile wallet.

In embodiments of the invention, a request may be made for a transactionvalue. For example, the request may be made by a mobile deviceprovisioned with pre-generated payment cards to a point of sale (POS)terminal. Based on the received transaction value, one of thepre-generated payment cards may be automatically selected by, forexample, a processor of the mobile device. The available credit limit ofthe selected card may be close to the transaction value. The availablecredit limit may be different than the maximum credit limit of theselected card. If previous purchases have been made using the selectedcard, the available credit limit may be the difference between theassigned credit limit of the selected card minus the total value of theprevious transactions. In some embodiments, a ratio of the transactionvalue to the available credit limit may be a pre-determined value. Inother embodiments, the payment card with the lowest allowable creditlimit may be selected. The lowest allowable credit limit may be justenough to conduct the transaction without exposing too large of a creditlimit during the transaction. For example, the available credit limit ofthe selected payment card may be slightly more or equal to thetransaction value. In some embodiments, the user may store the creditcards in a cloud wallet such as, for online transactions, where thelowest allowable credit card is used.

Embodiments of the invention may have a number of other features. Forexample, the selected payment card can be pre-generated and provisionedin a chip and personal identification number (PIN) card or a mobilewallet. The mobile wallet or the chip and PIN card may query the POSterminal for the value of the transaction. Upon receiving the value ofthe transaction, the mobile wallet or chip and PIN card mayautomatically select a payment card or a payment account and forward thepayment card information, e.g. the credit card number or the primaryaccount number (PAN) associated with the selected payment card, to thePOS terminal. In some embodiments, the user may select a payment card onthe mobile wallet to be used for each transaction.

As provided above, some embodiments may use a cloud wallet. The user mayupload details of payment cards as provided by the issuer into the cloudwallet. The user may use a wallet application to make an online purchasetransaction with minimum risk. A smart agent (e.g. a processor)associated with the mobile device or the cloud wallet may determine theavailable credit limits associated with the payment accounts and selecta payment card/account based on the transaction value such that theavailable credit limit of the selected payment card/account is close tothe transaction value. In some embodiments, the available credit limitof the selected payment card/account may be closer to the transactionvalue than the available credit limits of the other paymentcards/accounts. The available credit limit of the selected paymentcard/account is always equal to or greater than the transaction valuefor the transaction to be successfully completed.

Prior to discussing embodiments of the invention, description of someterms may be helpful in understanding embodiments of the invention.

As used herein, an “access device” may be any suitable device forcommunicating with a merchant computer or payment processing network,and for interacting with a payment device, a user computer apparatus,and/or a user mobile device. An access device may generally be locatedin any suitable location, such as at the location of a merchant. Anaccess device may be in any suitable form. Some examples of accessdevices include POS devices, cellular phones, PDAs, personal computers(PCs), tablet PCs, hand-held specialized readers, set-top boxes,electronic cash registers (ECRs), automated teller machines (ATMs),virtual cash registers (VCRs), kiosks, security systems, access systems,Websites, and the like. An access device may use any suitable contact orcontactless mode of operation to send or receive data from, orassociated with, a payment device and/or a user mobile device. In someembodiments, where an access device may comprise a POS terminal, anysuitable POS terminal may be used and may include a reader, a processor,and a computer-readable medium. A reader may include any suitablecontact or contactless mode of operation. For example, exemplary cardreaders can include radio frequency (RF) antennas, optical scanners, barcode readers, or magnetic stripe readers to interact with a paymentdevice and/or mobile device.

An “authorization request message” may be an electronic message that issent to a payment processing network and/or an issuer of a payment cardto request authorization for a transaction. An authorization requestmessage according to some embodiments may comply with ISO 8583, which isa standard for systems that exchange electronic transaction informationassociated with a payment made by a consumer using a payment device orpayment account. The authorization request message may include an issueraccount identifier that may be associated with a payment device orpayment account. An authorization request message may also compriseadditional data elements corresponding to “identification information”including, by way of example only: a service code, a CVV (cardverification value), a dCVV (dynamic card verification value), anexpiration date, etc. An authorization request message may also comprise“transaction information,” such as any information associated with acurrent transaction, such as the transaction value, merchant identifier,merchant location, etc., as well as any other information that may beutilized in determining whether to identify and/or authorize atransaction.

An “authorization response message” may be an electronic message replyto an authorization request message generated by an issuing financialinstitution or a payment processing network. The authorization responsemessage may include, by way of example only, one or more of thefollowing status indicators: Approval—transaction was approved;Decline—transaction was not approved; or Call Center—response pendingmore information, merchant must call the toll-free authorization phonenumber. The authorization response message may also include anauthorization code, which may be a code that a credit card issuing bankreturns in response to an authorization request message in an electronicmessage (either directly or through the payment processing network) tothe merchant's access device (e.g. POS equipment) that indicatesapproval of the transaction. The code may serve as proof ofauthorization. As noted above, in some embodiments, a payment processingnetwork may generate or forward the authorization response message tothe merchant.

As used herein, an “electronic wallet” or “digital wallet” can storeuser profile information, payment information, bank account information,and/or the like and can be used in a variety of transactions, such asbut not limited to eCommerce, social networks, money transfer/personalpayments, mobile commerce, proximity payments, gaming, and/or the likefor retail purchases, digital goods purchases, utility payments,purchasing games or gaming credits from gaming websites, transferringfunds between users, and/or the like.

As used herein, a “mobile device” may comprise any electronic devicethat may be transported and operated by a user, which may also provideremote communication capabilities to a network. Examples of remotecommunication capabilities include using a mobile phone (wireless)network, wireless data network (e.g. 3G, 4G or similar networks), Wi-Fi,Wi-Max, or any other communication medium that may provide access to anetwork such as the Internet or a private network. Examples of mobiledevices include mobile phones (e.g. cellular phones), PDAs, tabletcomputers, net books, laptop computers, personal music players,hand-held specialized readers, etc.

As used herein, an “online purchase” can be the purchase of a digital orphysical item or service via a network, such as the Internet.

As used herein, a “payment account” (which may be associated with one ormore payment devices) may refer to any suitable payment accountincluding a credit card account, a checking account, or a prepaidaccount.

As used herein, a “payment device” may refer to any device that may beused to conduct a financial transaction, such as to provide paymentinformation to a merchant. A payment device may be in any suitable form.For example, suitable payment devices can be hand-held and compact sothat they can fit into a consumer's wallet and/or pocket (e.g.,pocket-sized). They may include smart cards, magnetic stripe cards,keychain devices (such as the Speedpass™ commercially available fromExxon-Mobil Corp.), etc. Other examples of payment devices includecellular phones, personal digital assistants (PDAs), pagers, paymentcards, security cards, access cards, smart media, transponders, 2-Dbarcodes, an electronic or digital wallet, and the like. Such devicescan operate in either a contact or contactless mode.

As used herein, a “server computer” may include a powerful computer orcluster of computers. For example, the server computer can be a largemainframe, a minicomputer cluster, or a group of servers functioning asa unit. In one example, the server computer may be a database servercoupled to a web server. The server computer may be coupled to adatabase and may include any hardware, software, other logic, orcombination of the preceding for servicing the requests from one or moreclient computers. The server computer may comprise one or morecomputational apparatuses and may use any of a variety of computingstructures, arrangements, and compilations for servicing the requestsfrom one or more client computers.

Embodiments of the present invention described herein include multipledifferent embodiments that may be combined in any suitable manner, asone of ordinary skill in the art would recognize. For example, in thevarious embodiments described below, various different parties, paymentdevices, access devices, and transaction processors are described andspecific flow diagrams are provided as examples. These examples areprovided for illustration of the concepts of the present invention andare meant to be non-limiting. Accordingly, features from the variousembodiments may be combined in any suitable manner in differentconfigurations than are provided explicitly in each illustrative systemdescribed herein. Accordingly, just one example of the variouscombinations that could be provided according to some embodiments of thepresent invention is described in more detail below.

I. Payment Transaction Using a Dynamically Selected Account

Referring now to FIG. 1, a flowchart illustrating methods forautomatically selecting and using a payment card based on a transactionvalue is provided according to various embodiments of the invention.Throughout the description, the terms “payment card” and “paymentaccount” are used interchangeably. Although a credit payment device isdescribed in detail, it is understood that embodiments of the inventionmay be used for any type of payment cards, including but not limited tostored value cards, debit cards, etc.

A method of using a payment device 32 (e.g., user mobile device, aportable consumer payment device, etc.) at an access device 34 (e.g.,POS terminal) can be described as follows.

In step S102, a user may attempt to pay for goods and services providedby a merchant. The merchant may be a mortar-and-brick store or an onlinestore. The user presents his or her payment device 32 to an accessdevice 34 of the merchant to pay for the item or service. Beforetransmitting a primary account number and other payment data to theaccess device 34, the payment device 32 may transmit a request to theaccess device 34 to obtain the transaction value and/or otherinformation about the transaction.

In step S104, the access device 34 provides the transaction value and/orthe requested information about the transaction to the payment device32. The transaction value may be provided by the access device 34 in anysuitable manner. For example, the payment device 32 may take a pictureof the transaction value or a code (e.g., a barcode) representing thetransaction value. Alternatively, the access device 34 may pass thetransaction value to the payment device 32 through a contact-based orcontactless-based communication medium.

In step S106, a processor in the payment device 32 can automaticallyselect a payment account from a plurality of payment accountsprovisioned on the payment device 32. For example, four credit cardaccounts with available credit limits of $25, $100, $250, and $500,respectively may be provisioned on the payment device 32. The creditcard accounts may belong to separate payment accounts or, alternatively,the credit card accounts may be derived from a parent credit cardaccount.

If the received transaction value is $99, then the processor in thepayment device 32 may automatically select the credit account associatedwith the $100 credit limit. By doing so, the payment device 32 selectsan account that has sufficient credit to pay for the transaction, butvery little credit limit is exposed after the transaction is conducted.In this example, only $1 in credit is left on the $100 credit cardaccount until the user pays his balance on the credit card account. Ifan unauthorized party steals and tries to use the credit card numberwith the remaining $1 credit limit, the credit card number will bedeclined for any purchases over $1. Consequently, the risk to the userand the issuer that issued the credit card account is advantageouslyreduced.

In step S108, the payment device 32 provides the payment account number(or other payment account identifier) to the access device 34. Forexample, the payment device 32 may provide (e.g. transmit) the PAN, CVV,expiration date and other data (e.g., cryptograms, etc.) associated withthe selected payment account to the access device 34.

The merchant computer 22 may then receive the information including thePAN of the selected credit card account along with the associated CVV,expiration date and other data at step S110 from the access device 34.If the access device 34 has not already generated an authorizationrequest message, the merchant computer 22 may then generate anauthorization request message that includes the information receivedfrom the access device 34 along with additional transaction information(e.g., a transaction value, merchant specific information, etc.) and atstep S112 electronically transmit this information to an acquirercomputer 24. At step S114, the acquirer computer 24 may receive andprocess the authorization request message. At step S116, the acquirercomputer 24 may forward the processed authorization request message tothe issuer computer 28 via a payment processing network 26 forauthorization. The issuer computer 28 generates an authorizationresponse message and forwards the authorization response message to thepayment processing network 26 (step S118). At steps S120, S122, andS124, the authorization response message is sent from the paymentprocessing network 26 to the access device 34 via the acquirer computer24 and the merchant computer 22.

At a later time, after authorization, a clearing and settlement processmay be performed between the payment processing network 26, and acquireroperating the acquirer computer 24 and the issuer operating the issuercomputer 28.

II. Exemplary Payment Devices

Provided below are descriptions of some devices (and components of thosedevices) that may be used in the systems and methods described above.These devices may be used, for instance, to receive, transmit, process,and/or store data related to any of the functionality described above.As would be appreciated by one of ordinary skill in the art, the devicesdescribed below may have only some of the components described below, ormay have additional components.

According to various embodiments of the present application, the paymentdevice 32 may include a portable consumer payment device such as apayment card. The payment card may include, but is not limited to asmart card, a security card, a credit card or a debit card. An exemplaryembodiment of a portable consumer payment device provisioned withmultiple payment accounts with different credit limits is illustrated inFIG. 2. In other embodiments, the payment device 32 may include a mobiledevice. The mobile device may include, but is not limited to, a cellularphone, a smart phone, a tablet or a portable computing device. Anexemplary embodiment of a mobile device provisioned with multiplepayment accounts with different credit limits is illustrated in FIG. 3.

As provided above, FIG. 2 illustrates the payment device 32 including aportable consumer payment device 33. The portable consumer paymentdevice 33 may include a memory chip 33(e) to store a plurality ofseparate credit card account numbers. The portable consumer paymentdevice 33 may also include expiration dates and card verification values(CVVs) associated with the four separate credit card account numbers. Inthe illustrated example, the four credit card account numbers may havecredit limits of $25, $100, $250, and $500, respectively. These creditcard account numbers may stand alone, or they may be derived from aparent credit card account as shown in FIG. 2. In the illustratedexample, the parent credit card account may have a credit limit of$5000, and the $25, $100, $250, and $500 credit limits associated withthe four derived credit card numbers may constitute portions of the$5000 credit limit.

FIG. 2 illustrates the portable consumer payment device 33 in the formof a plastic substrate 33(b). In some embodiments, a contactless element33(f) for interfacing with an access device 34 may be present on, orembedded within, the plastic substrate 33(b). Consumer information 33(c)such as an account number, expiration date, and/or a user name may beprinted or embossed on the portable consumer payment device 33. As shownin FIG. 2, the portable consumer payment device 33 may include both amagnetic stripe 33(a) and a contactless element 33(f). In someembodiments, both the magnetic stripe 33(a) and the contactless element33(f) may be on the portable consumer payment device 33. In someembodiments, either the magnetic stripe 33(a) or the contactless element33(f) may be present on the portable consumer payment device 33.

The portable consumer payment device 33 may also include amicroprocessor 33(d). The microprocessor 33(d) may include logic toselect one of the plurality of separate credit card account numbers fora transaction, based on the transaction value. For example, themicroprocessor 33(d) may request and subsequently receive thetransaction value for a transaction from the access device 34. If thereceived transaction value is $99, the microprocessor 33(d) mayautomatically select the credit card account number associated with the$100 available credit limit to be able to pay for the transaction valuewhile exposing minimum residual credit limit. That is, themicroprocessor 33(d) may select the credit card account where the limitis closest to and greater than the transaction value.

In some embodiments, the microprocessor 33(d) may automatically selectthe credit account number having an available credit limit in apre-determined range of the transaction value. For example, themicroprocessor 33(d) may automatically select the credit account numberwith an available credit limit 5% greater than the transaction value.

In yet other embodiments, the microprocessor 33(d) may automaticallyselect the credit account number based on the transaction value andmerchant information. For example, the merchant information may indicatethat the merchant is a non-local merchant (e.g. an online merchant or amerchant in a foreign state) or a non-trusted merchant. Themicroprocessor 33(d) may be programmed to automatically select thecredit account number with an available credit limit 0.1% above thetransaction value for a non-local or non-trusted merchant. Themicroprocessor 33(d) may have access to a list of merchants to querywhether the merchant is a non-local merchant or a non-trusted merchant.For example a list of merchants may be stored at memory chip 33(e).Alternatively, a list of merchants may be stored at a remote data baseor data store accessible by the microprocessor 33(d).

As provided above, in some embodiments, the payment device 32 mayinclude a mobile device such as a cellular phone, a smart phone, atablet or a portable computing device. FIG. 3 illustrates such anexemplary embodiment.

Referring now to FIG. 3, the payment device 32 may include a mobiledevice 36 such as a mobile phone. The mobile device 36 may include, butis not limited to, a mobile phone, a tablet, a notification device thatcan receive alert messages, and/or a multi-purpose general use devicethat can be used to make payments. The exemplary mobile device 36 maycomprise a computer readable medium 36(b) that be present within thebody (or outer casing) of the mobile device 36. Alternatively, thecomputer readable medium 36(b) could be detachable from the device. Forexample, the computer readable medium 36(b) could comprise an externalmemory that could be connected through a physical interface such as aUSB connection, or the data could be hosted remotely and accessedwirelessly by the device—e.g. the data could be hosted and stored at aremoter server in the “cloud”. The computer readable medium 36(b) may bein the form of a memory that stores data.

In addition to the computer readable medium 36(b), the mobile device 36may include a separate memory 36(j) that may store information such asfinancial information, transit information (e.g., as in a subway ortrain pass), access information (e.g., access badges), serial numbers,mobile account information, and any other suitable information.According to various embodiments, the memory 36(j) may store informationfor a plurality of payment accounts 360. For example, the paymentaccounts 360 may include a plurality of credit card accounts associatedwith a plurality of credit card account numbers. The memory 36(j) maystore the credit card account numbers along with the associatedexpiration dates and CVVs. At least two of the stored credit cardaccount numbers may be associated with a different credit limit. In someembodiments, each of the plurality of credit card account numbers may beassociated with a different credit limit. In some embodiments, thememory 36(j) may store merchant information 362. The merchantinformation 362 may be used in selecting one of the plurality of creditcard account numbers for a transaction, as discussed further below.

The mobile device 36 may include a processor 36(c) (e.g., amicroprocessor) for performing the functions of the phone 36 and forautomatically selecting one of the credit card account numbers stored inthe memory 36(j). For example, the processor 36(c) may include selectionlogic 368 for automatically selecting one of the credit card accountnumbers based on a transaction value received from an access device,e.g. a POS terminal. If the received transaction value is $99, theprocessor 36(c) may automatically select the credit card account numberassociated with the $100 available credit limit to be able to pay forthe transaction while exposing minimum residual credit limit. That is,the processor 36(c) may select the credit card account where the limitis closest to and greater than the transaction value.

In some embodiments, the processor 36(c) may automatically select thecredit account number having an available credit limit in apre-determined range of the transaction value. For example, theprocessor 36(c) may automatically select the credit account number witha credit limit 5% greater than the transaction value.

In yet other embodiments, the processor 36(c) may automatically selectthe credit account number based on the transaction value and merchantinformation. For example, the merchant information may indicate that themerchant is a non-local merchant (e.g. an online merchant or a merchantin a foreign state) or a non-trusted merchant. The processor 36(c) maybe programmed to automatically select the credit account number with acredit limit 0.1% above the transaction value for a non-local ornon-trusted merchant. The processor 36(c) may have access to a list ofmerchants to query whether the merchant is a non-local merchant or anon-trusted merchant. For example a list of merchants may be stored inmemory 36(j). Alternatively, a list of merchants may be stored at aremote data base or data store accessible by the processor 36(c). Theprocessor 36(c) may include comparison logic 366 for comparing themerchant information to the information in the list of merchants.

In general, any of the information stored in the computer readablemedium 36(b) or the memory 36(j) may be transmitted by the mobile device36 to an access device 34, via any suitable method, including the use ofantenna 36(a) or contactless element 36(g). The contactless element36(g) may be implemented in the form of a semiconductor chip (or otherdata storage element) with an associated wireless transfer (e.g., datatransmission) element, such as an antenna. Contactless element 36(g) maybe coupled to (e.g., embedded within) the mobile device 36 and data orcontrol instructions that are transmitted via a cellular network may beapplied to the contactless element 36(g) by means of a contactlesselement interface (not shown). The contactless element interfacefunctions to permit the exchange of data and/or control instructionsbetween the mobile device circuitry and an optional contactless element36(g), or between another device having a contactless element (e.g. aPOS terminal or a payment device). Contactless element 36(g) may becapable of transferring and receiving data using a short range wirelesscommunication capability. As noted above, mobile device 36 may comprisecomponents to both be the interrogator device (e.g. receiving data) andthe interrogated device (e.g. sending data). Thus, the mobile device 36may be capable of communicating and transferring data or controlinstructions via both cellular network (or any other suitable wirelessnetwork—e.g. the Internet or other data network) and short rangecommunications.

The mobile device 36 may also include a display 36(d) to allow aconsumer to see payment account numbers and other information. Themobile device 36 may further include input elements 36(e) to allow auser to input information into the device, a speaker 36(f) to allow theuser to hear voice communication, music, etc., and a microphone 36(i) toallow the user to transmit her voice through the mobile device 36.

As provided above, in some embodiments, the plurality of credit cardaccount numbers may be provided on a mobile wallet. FIG. 4 illustratesan exemplary embodiment of a mobile wallet 400. The mobile wallet 400may be provided by a mobile wallet application and the user interfacefor the mobile wallet 400 may be shown in FIG. 4. Specifically, FIG. 4shows an exemplary embodiment where a plurality of credit cards 404,406, 408 and 410 are provided on a mobile wallet 400 that is resident ona payment device 32. As discussed above, the payment device 32 mayautomatically select the most appropriate credit card based on at leastthe transaction value. For example, in the example illustrated in FIG.4, if the transaction value is $40, the credit card 404 with anavailable credit limit of $50 is automatically selected and presentedfor the transaction being conducted. The mobile wallet 400 may have adedicated area 402 to display the selected credit card information asthe funding source for the transaction being conducted. In someembodiments, the user may have the option to change the selected creditcard and select a new credit card to be used for the transaction. Theuser may not be limited to the credit card accounts displayed on themobile wallet 400. The user may add other credit cards or remove creditcards from the ones currently included in the mobile wallet 400.

In some embodiments, for a given transaction value, the payment device32 may automatically select a payment account based on the paymentaccount number. For example, payment processing network operators, suchas Visa Inc. and other partners, may assign pre-determined credit limitsto the payment cards based on the account numbers. As illustrated inFIG. 4, a payment card ending in 5555 may have a low credit limit (e.g.,$5). Another card ending in 3333 may have a higher credit limit (e.g.$10,000). Accordingly, the payment device 32 may use the last digitsinformation (in addition to the transaction value) in determining whichcredit card account should be selected. In various embodiments, thepayment device 32 may also use risk algorithms and routing decisionsbased on the transaction value and information about the card number.

III. Dynamic Account Selection

According to various embodiments, a mobile device may be provisionedwith pre-generated payment cards (real or virtual) or payment accountnumbers with different credit limits. FIG. 5 illustrates a flowchart 500of a method for automatically selecting a payment card among a pluralityof payment cards based on at least a transaction value. FIG. 6 shows aflowchart 600 of a method for receiving an automatically selectedpayment card for a transaction in response to sending the transactionvalue to a user device.

Referring now to FIG. 5, while conducting a payment transaction, apayment device may request information about the transaction (step 502).The requested information may include the transaction value for a goodor service that is being purchased (acquired). The requested informationmay also include merchant information such as the merchant name andlocation, merchant security rating, etc. The payment device may requestthe transaction information from an access device such as a POSterminal. At step 504, the payment device may receive the informationabout the transaction including the transaction value. Alternatively,the payment device may use the received transaction information todetermine the transaction value instead of receiving the transactionvalue directly from the access device. In some embodiments, thetransaction value may be provided to the payment device without thepayment device requesting the information.

The payment device may store a plurality of payment cards or paymentaccounts associated with different credit limits. In embodiments of theinvention, there may be at least two, three, four, five, or six or morepayment accounts or cards available for selection on a payment device.At step 506, the payment device may compare the transaction value to thecredit limits of the plurality of payment cards to select one of theplurality of the payment cards to be used for the transaction.

To compare the available credit limits of a plurality of payment cardsor payment accounts with the transaction value, the available creditlimits of each of the cards or accounts needs to be determined. Theavailable credit limit for a particular card may be different than themaximum (i.e. assigned) credit limit for that card. For example, acardholder may never have a credit limit over $10,000 (the maximumcredit limit) for a particular payment account. By comparison, theactual credit limit may be $5000 of the maximum credit limit $10,000 and$5000 of prior purchases has already been made on the account, but havenot yet been paid by the cardholder.

The determination of the available credit limit for each payment accountcan occur in any suitable manner. In some cases, a mobile walletapplication on a phone may have a transaction log for each paymentaccount, and the transaction log may keep track of the available creditlimit for each account. The transaction log may be updated periodicallywhen the payment device is online and can communicate with the remoteserver at the issuer of the account. In other embodiments, the availablecredit limit may be determined by querying the wallet server or theissuer's computer just prior to or during the transaction beingconducted. For example, if the payment device is a mobile phone, thenthe mobile phone may communicate with a wallet server or issuer computerover the air or through the Internet (e.g., through WiFi) to retrievethe current available credit limits for all accounts associated with thepayment device.

In some embodiments, if the payment device received additionalinformation about the transaction, the payment device may query a datastore for predetermined selection criteria or merchant information (step508). For example, if the received transaction information includesinformation about the merchant, the payment device may query a merchantdatabase to determine whether the merchant is a non-local merchant or anon-trusted merchant. The merchant database may be stored at the paymentdevice or may be stored at a remote location accessible by the paymentdevice. If the payment device determines that the merchant is anon-trusted or a non-local merchant with a low merchant rating, thepayment device may select one of the plurality of the payment cards tobe used for the transaction based on the merchant rating in addition tothe transaction value.

At step 510, the payment device may automatically select a payment cardamong the plurality of payment cards stored at the payment device basedon the transaction value. The selected payment card may have anavailable credit limit that is close to the transaction value. In someembodiments, the payment device may automatically select the paymentcard with the closest credit limit to the transaction value. Theavailable credit limit of the payment card is greater than or equal tothe transaction value to be able to complete the transaction.

Once the payment card is selected, the payment device may providepayment account data associated with the selected payment card to themerchant to complete the transaction (step 512).

Although the specific examples described above refer to the use ofpayment account numbers, it is understood that payment tokens may beused in place of payment account numbers. Payment tokens may beencrypted or random values associated with payment account numbers, andthey may or may not have the same format as real payment account numbers

Referring now to FIG. 6, while conducting a payment transaction, anaccess device of a merchant may receive a request for a transactionvalue (step 602). The request may be received from a payment device suchas a mobile device of a user. In some embodiments, the request may alsoinclude a request for additional information such as merchant location,merchant name, merchant rating (if applicable) and other informationabout the transaction. At step 604, the access device may provide thetransaction value (and other information, if requested) to therequester. Subsequently, at step 606, the access device may receivepayment account data to be used in the transaction. The payment accountdata may have an available credit limit that is close to the transactionvalue. The available credit limit is greater than or equal to thetransaction value in order to be able to complete the transaction. Atstep 608, the access device may process the transaction (e.g., bygenerating an authorization request message and transmitting it to anissuer for approval, as described above with respect to FIG. 1).

IV. Additional Exemplary System Embodiments

Provided below is a description of an exemplary system in whichembodiments provided herein may be utilized. Although some of theentities and components may be depicted as separate, in some instances,one or more of the components may be combined into a single device orlocation (and vice versa). Similarly, although certain functionality maybe described as being performed by a single entity or component withinthe system, the functionality may in some instances be performed bymultiple components and/or entities (and vice versa). Communicationbetween entities and components may comprise the exchange of data orinformation using electronic messages and any suitable electroniccommunication medium and method, as described below.

As used herein, an “issuer” may typically refer to a business entity(e.g., a bank or other financial institution) that maintains financialaccounts for the user 702 and often issues a payment device 32 such as acredit card to the user 702. As used herein, a “merchant” may typicallyrefer to an entity that engages in transactions and can sell goods orservices to the user 702. As used herein, an “acquirer” may typicallyrefer to a business entity (e.g., a commercial bank or financialinstitution) that has a business relationship with a particular merchantor similar entity. Some entities can perform both issuer and acquirerfunctions.

An exemplary financial transaction system is shown in FIG. 7. The system700 may include one or more merchants, one or more access devices 34,one or more payment devices 32, one or more acquirers, and one or moreissuers. For example, the system 700 may include a merchant having amerchant computer 22 that comprises an external communication interface(e.g., for communicating with an access device 34 and an acquirer 24),system memory comprising one or modules to generate and utilizeelectronic messages, and a data processor (for facilitating a financialtransaction and the exchange of electronic messages); an acquirer havingan acquirer computer 24 that comprises an external communicationinterface (e.g. for communicating with a merchant computer 22 and apayment processing network 26), system memory comprising one or modulesto generate and utilize electronic messages, and a data processor (forfacilitating a financial transaction and the exchange of electronicmessages); and an issuer having an issuer computer 28 that comprises anexternal communication interface (e.g. for communicating with a paymentprocessing network 26), system memory comprising one or modules togenerate and utilize electronic messages, and a data processor (forfacilitating a financial transaction and the exchange of electronicmessages). The external communication interface of the merchant computer22 may be coupled to an access device 34 (such that information may bereceived by the access device 34 and communicated to the merchantcomputer 22) or, in some embodiments, the access device 34 may comprisea component of the merchant computer 22.

As used in this context, an external communication interface may referto any hardware and/or software that enables data to be transferredbetween two or components of system 700 (e.g., between devices residingat locations such as an issuer, acquirer, merchant, payment processingnetwork 26, etc.). Some examples of external communication interfacesmay include a modem, a network interface (such as an Ethernet card), acommunications port, a Personal Computer Memory Card InternationalAssociation (PCMCIA) slot and card, or the like. Data transferred viaexternal communications interface may be in the form of signals whichmay be electrical, electromagnetic, optical, or any other signal capableof being received by the external communications interface (collectivelyreferred to as “electronic signals” or “electronic messages”). Theseelectronic messages that may comprise data or instructions may beprovided between one or more of the external communications interfacevia a communications path or channel. As noted above, any suitablecommunication path or channel may be used such as, for instance, a wireor cable, fiber optics, a telephone line, a cellular link, a radiofrequency (RF) link, a WAN or LAN network, the Internet, or any othersuitable method.

Any suitable communications protocol for storing, representing, andtransmitting data between components in the system 700 may be used. Someexamples of such methods may include utilizing predefined and staticfields (such as in core TCP/IP protocols); “Field: Value” pairs (e.g.,HTTP, FTP, SMTP, POP3, and SIP); an XML based format; and/orTag-Length-Value format.

As shown in the exemplary system 700 in FIG. 7, information from thecredit payment device 32 may be provided to the access device 34 eitherdirectly (e.g., through a contact or contactless interface) orindirectly through a user computer or mobile device (e.g. in ane-commerce environment or other indirect transaction) via network 40(such as the Internet). In some embodiments, the user computer or mobiledevice may interact with the payment processing network 26 (or otherentity in the system 700) via the network 40 to form a firstcommunications channel, such as through an Internet Protocol Gateway(IPG) 27. The IPG 27 may be in operative communication with the paymentprocessing network 26. Although the IPG 27 is shown as being a separateentity in FIG. 7, the IPG 27 could be incorporated into the paymentprocessing network 26, or could be omitted from the system 700. In thelatter situation, the first communications channel could directlyconnect the payment processing network 26 and the user computer ormobile device. In general, providing communication from the user 702 tothe payment processing network or other entity may enable a variety ofincreased functionalities to the user 702, such as advancedauthentication and verification methods (particularly in e-commerce andsimilar transactions), examples of which are described in U.S. Ser. No.12/712,148 filed on Jul. 16, 2010 and U.S. Ser. No. 13/184,080 filed onJul. 15, 2011, each of which is incorporated by reference herein in itsentirety.

In some embodiments, an electronic or digital wallet (i.e., “e-Wallet”)may be utilized as a payment device for conducting a financialtransaction. As shown in FIG. 7, such exemplary systems may comprise anelectronic wallet server 29, which may be accessible to the user 702 vianetwork 40 (either directly connected or through an IPG 27) and may alsobe in operational communication with a merchant and/or with a paymentprocessing network 26 (or in some embodiments, the electronic walletserver 29 may comprise a part of the payment processing network 26). Theelectronic wallet server 29 may be programmed or configured to providesome or all of the functionality associated with conducting transactionsusing an electronic wallet, including maintaining an association betweenthe user's E-wallet and one or more payment accounts (such as a bankaccount or credit card account) in the E-Wallet database 31. To provideelectronic wallet services (i.e. the use of the electronic walletassociated with a payment account to conduct a financial transaction),the electronic wallet server 29 may further provide a web interface(e.g. through one or more web pages) to receive and transmit requestsfor payments services and/or may provide an application programinterface (API) (shown as electronic wallet client 37) at the paymentdevice 32 to provide the web service. This process is described in moredetail in U.S. Application No. 61/466,409 filed on Mar. 22, 2011, whichis incorporated herein by reference in its entirety.

As noted above, the user's electronic wallet may be stored in theE-Wallet database 31, which may include information associated with theuser's payment accounts, and can be used in conducting a financialtransaction with a merchant. For example, the E-Wallet database 31 mayinclude the primary account numbers of one or more payment accounts(e.g., payment accounts associated with a credit card) of the user 702.The E-wallet may be populated with such information during an initialenrollment process in which the user 702 enters information regardingone or more of the payment accounts that may be associated with variousissuers. Once the payment account information is added to the E-Walletdatabase 31, the user 702 may perform transactions by utilizing only hisE-wallet. When a user 702 performs a transaction using his electronicwallet, the user 702 need not provide the merchant with payment accountinformation, but may instead provide the electronic wallet information.This information may then be included in an authorization requestmessage, which in turn may be provided to payment processing network 26.The payment processing network 26 may then access the user's E-walletvia a request to the electronic wallet server 29, or may have directaccess to the E-wallet database 31 so as to obtain the correspondingpayment account information indicated by the information in theauthorization request message.

The electronic wallet client 37 may comprise any suitable software thatprovides front end functionality of the electronic wallet to the user702. For example, the electronic wallet client 37 may be embodied as asoftware application downloadable by a computer apparatus or mobiledevice 32 (e.g., a mobile phone). In some instances, the electronicwallet client 37 may provide a user interface (such as a series of menusor other elements) that allows the user 702 to manage his electronicwallet(s) (i.e. the electronic wallet client 37 may enable interactionwith the electronic wallet server 29, and thereby the e-wallet database31). In some embodiments, the electronic wallet client 37 may store datain a computer readable memory for later use, such as user 702preferences or identifiers associated with funding sources added to theelectronic wallet.

As provided above, in some embodiments, the payment device 32 may querythe issuer computer 28 and/or the e-wallet database 31 via network 40(either directly connected or through the IPG 27) to determine theavailable credit limit for each payment account. The payment device 32may retrieve the current available credit limits for one or moreaccounts associated with the payment device 32 from the issuer computer28 and/or the e-wallet database 31. The payment device 32 may alsoprovide update about payment transactions to the issuer computer 28and/or the e-wallet database 31 via network 40. This way, the issuercomputer 28 and/or the e-wallet database 31 may update their records anddeduct the amount of any additional payment(s) made using a givenpayment account from the available credit associated with the givenpayment account.

A payment processing network 26 may be disposed between the acquirercomputer 24 and the issuer computer 28 in the system 700. Furthermore,the merchant computer 22, the acquirer computer 24, the paymentprocessing network 26, and the issuer computer 28 may all be inoperative communication with each other (i.e., although not depicted inFIG. 7, one or more communication channels may exist between each of theentities, whether or not these channels are used in conducting afinancial transaction).

The payment processing network 26 may include data processingsubsystems, networks, and operations used to support and deliverauthorization services, exception file services, and clearing andsettlement services. For example, the payment processing network 26 maycomprise a server computer, coupled to a network interface (e.g. by anexternal communication interface), and a database(s) of information. Anexemplary payment processing network may include VisaNet™. Paymentprocessing networks such as VisaNet™ are able to process credit cardtransactions, debit card transactions, and other types of commercialtransactions. VisaNet™, in particular, includes a VIP system (VisaIntegrated Payments system) which processes authorization requests and aBase II system which performs clearing and settlement services. Thepayment processing network 26 may use any suitable wired or wirelessnetwork, including the Internet.

V. Exemplary Computer Apparatuses

FIG. 8 shows some components in a computer apparatus. The computerapparatus may be used in any of the components illustrated in FIGS. 1, 3and 7, and such components may use any suitable combination or number ofsubsystems shown in FIG. 8. The subsystems shown in FIG. 8 areinterconnected via a system bus 775. Additional subsystems such as aprinter 774, keyboard 778, fixed disk 779 (or other memory comprisingcomputer readable media), monitor 776, which is coupled to displayadapter 782, and others are shown. Peripherals and input/output (I/O)devices, which couple to I/O controller 771 (which can be a processor orother suitable controller), can be connected to the computer system byany number of means known in the art, such as serial port 777. Forexample, serial port 777 or external interface 781 can be used toconnect the computer apparatus to a wide area network such as theInternet, a mouse input device, or a scanner. The interconnection viasystem bus allows the central processor 773 to communicate with eachsubsystem and to control the execution of instructions from systemmemory 772 or the fixed disk 779, as well as the exchange of informationbetween subsystems. The system memory 772 and/or the fixed disk 779 mayembody a computer readable medium.

The above description is illustrative and is not restrictive. Manyvariations of the invention will become apparent to those skilled in theart upon review of the disclosure. The scope of the invention should,therefore, be determined not with reference to the above description,but instead should be determined with reference to the pending claimsalong with their full scope or equivalents.

A recitation of “a,” “an,” or “the” is intended to mean “one or more”unless specifically indicated to the contrary. Reference to a “first”component does not necessarily require that a second component beprovided. Moreover reference to a “first” or a “second” component doesnot limit the referenced component to a particular location unlessexpressly stated.

All publications mentioned herein are incorporated herein by referenceto disclose and describe the methods and/or materials in connection withwhich the publications are cited.

What is claimed is:
 1. A method comprising: receiving, using a processorof a payment device, information about a plurality of payment accountsderived from a parent payment account; storing, at a secure memoryelement of the payment device, the information about the plurality ofpayment accounts thereby provisioning the plurality of payment accountson the payment device; communicating, using a contactless element of thepayment device, with an access device of a merchant to conduct atransaction; receiving, using the processor of the payment device,information about the transaction from the access device, theinformation including a transaction value, and also receiving merchantinformation; comparing, using the processor of the payment device, thetransaction value to a plurality of available limits associated with theplurality of payment accounts, wherein the plurality of available limitsconstitute portions of an available limit of the parent payment account;determining, whether the merchant is a trusted or non-trusted merchantbased on the received the merchant information; automatically selecting,using the processor of the payment device, a selected payment accountamong the plurality of payment accounts based on an available limitassociated with the selected payment account being higher than thetransaction value by a predetermined amount, wherein the predeterminedamount is higher when the merchant is a local or trusted merchant thanwhen the merchant is a non-local or non-trusted merchant; and providing,by the processor of the payment device, payment account data associatedwith the selected payment account to the access device.
 2. The method ofclaim 1, further comprising: prior to comparing: determining, using theprocessor, the plurality of available limits associated with theplurality of payment accounts, wherein an available limit associatedwith a payment account is different than an assigned limit to thepayment account, wherein a value of the available limit is less than orequal to a value of the assigned limit.
 3. The method of claim 1 whereinthe available limit is a credit limit and the selected payment accountis a credit card account.
 4. The method of claim 1 wherein the accessdevice is a POS terminal.
 5. The method of claim 1 further comprising:querying, using the information about the transaction, a data storagefor the merchant information, wherein the information about thetransaction includes one or more of a merchant name, a merchant address,a merchant identification number, and a merchant rating.
 6. The methodof claim 5 wherein the merchant is a non-trusted merchant.
 7. The methodof claim 6 wherein the payment device is a mobile phone.
 8. A methodcomprising: receiving, using a contactless element of a user device,information about a merchant and a transaction value for a transactionbetween the merchant and a user of the user device; determining, using aprocessor of the user device, a plurality of available limits associatedwith a plurality of payment accounts, wherein an available limitassociated with a payment account is different than an assigned limit tothe payment account, wherein a value of the available limit is less thanor equal to a value of the assigned limit; comparing, using a comparisonlogic executed by the processor, the transaction value to the pluralityof available limits associated with the plurality of payment accountsderived from a parent payment account, wherein the plurality ofavailable limits constitute portions of an available limit of the parentpayment account; automatically selecting, using a selection logicexecuted by the processor, a selected payment account among theplurality of payment accounts based on an available limit associatedwith the selected payment account being higher than the transactionvalue by a predetermined amount, wherein the predetermined amountdepends on the information about the merchant; and providing, by theprocessor, payment account data associated with the selected paymentaccount to an access device of the merchant.
 9. The method of claim 8,wherein the predetermined amount has a first value when the informationabout the merchant indicates that the merchant is a non-local merchantand a second value when the information about the merchant indicatesthat the merchant is a local merchant, such that the first value issmaller than the second value.
 10. A mobile device comprising: aprocessor, a secure memory element, a contactless element; and acomputer readable medium coupled to the processor, the computer readablemedium comprising code that, when executed on the processor, causes theprocessor to implement a method comprising receiving, using theprocessor, information about a plurality of payment accounts derivedfrom a parent payment account; storing, at the secure memory element,the information about the plurality of payment accounts therebyprovisioning the plurality of payment accounts on the mobile device;communicating, using the contactless element, with an access device of amerchant to conduct a transaction; receiving, using the processor,information about the transaction, the information including atransaction value from the access device, and receiving merchantinformation, comparing, using the processor, the transaction value to aplurality of available limits associated with the plurality of paymentaccounts, wherein the plurality of available limits constitute portionsof an available limit of the parent payment account; determining,whether the merchant is a trusted or non-trusted merchant based on thereceived the merchant information; automatically selecting, using theprocessor, a selected payment account among the plurality of paymentaccounts based on an available limit associated with the selectedpayment account being higher than the transaction value by apredetermined amount, wherein the predetermined amount is higher whenthe merchant is a local or trusted merchant than when the merchant is anon-local or non-trusted merchant; and providing, by the processor,payment account data associated with the selected payment account to theaccess device.
 11. The mobile device of claim 10 wherein the availablelimit is an available credit limit and the selected payment account is acredit card account.
 12. The mobile device of claim 10 wherein the code,when executed on the processor, further causes the processor to: query,using the information about the transaction, a data storage for themerchant information, wherein the information about the transactionincludes one or more of a merchant name, a merchant address, a merchantidentification number, and a merchant rating.
 13. The mobile device ofclaim 10 wherein the selected payment account is selected such that theavailable limit of the selected payment account is within apredetermined range of the transaction value.